Process scheduling based on file system consistency level

ABSTRACT

An approach for modifying a scan schedule involving receiving first results of a first file system scan of one or more computer systems, comparing the first results to second results of a previous file system scan of the one or more computer systems, computing a file system change value based on comparing the first results to the second results of the previous file system scan and modifying a frequency of a file system scan schedule based on the file system change value.

BACKGROUND

The present invention relates generally to the field of softwareassessment products, and more particularly to scheduled file scans.

Software assessment products are products which can perform scans offile systems on computer systems to determine information about thefiles contained therein, information such as, but not limited to, aquantification of different file types. One such example of a softwareassessment product is License Metric Tool by International BusinessMachines Corporation, a product designed to assist customers of PassportAdvantage by International Business Machines Corporation to maintaincompliance with the license requirements of the service through aregular file system scans on customer computer systems. File systemscans performed by software assessment products can be manually runanytime or they can be configured to automatically run on apredetermined schedule, according to a frequency determined appropriateby a customer, for example.

SUMMARY

According to one embodiment of the present invention, a method formodifying a scan schedule is provided, the method comprising receivingfirst results of a first file system scan of one or more computersystems; comparing the first results to second results of a previousfile system scan of the one or more computer systems; computing a filesystem change value based on comparing the first results to the secondresults of the previous file system scan; and modifying a frequency of afile system scan schedule based on the file system change value. Acorresponding computer program product and computer system are alsodisclosed herein.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a functional block diagram illustrating a distributed dataprocessing environment, in accordance with an embodiment of the presentinvention;

FIG. 2 is a flowchart depicting operational steps of a schedule modifieron a computer system within the data processing environment of FIG. 1,in accordance with an embodiment of the present invention;

FIG. 3 is a flowchart illustrating computational processes of theschedule modifier, in accordance with an embodiment of the presentinvention; and

FIG. 4 is a block diagram of components of the computer system executingthe intelligent mapping program, in accordance with an embodiment of thepresent invention.

DETAILED DESCRIPTION

Embodiments of the present invention recognize that software assessmentproducts, which can run on one or more computer systems, do notpresently consider the volume of file system changes, associated withthe one or more computer systems, in determining a schedule for filesystem scans. Some computer systems, e.g., production servers, may havestable file systems with very few file changes occurring between scans,while other computer systems, e.g., development and test servers, mayundergo more frequent and numerous file changes between scans. It iswith this in mind that embodiments of the present invention provide asolution to determine and configure an appropriate schedule for asoftware assessment product to run a file system scan on one or morecomputer systems, based on the amount of measurable file system changes,i.e., the rate of file changes, associated with those one or morecomputer systems between scans.

In describing embodiments in detail with reference to the figures, itshould be noted that references in the specification to “an embodiment,”“other embodiments,” etc., indicate that the embodiment described mayinclude a particular feature, structure, or characteristic, but everyembodiment may not necessarily include the particular feature,structure, or characteristic. Moreover, such phrases are not necessarilyreferring to the same embodiment. Further, describing a particularfeature, structure or characteristic in connection with an embodiment,one skilled in the art has the knowledge to affect such feature,structure or characteristic in connection with other embodiments whetheror not explicitly described.

The present invention will now be described in detail with reference tothe figures. FIG. 1 is a functional block diagram illustrating adistributed data processing environment 100, in accordance with oneembodiment of the present invention. Distributed data processingenvironment 100 includes computer system 102 and server computer 111,interconnected over network 110. It should be noted that computer system102 can generally be representative of any number of computer systems.

Computer system 102 can be a laptop computer, tablet computer, netbookcomputer, personal computer (PC), a desktop computer, a personal digitalassistant (PDA), a smart phone, or any programmable electronic devicecapable of communicating with server computer 111 via network 110.Computer system 102 comprises software assessment product 104 fordetermining information about files associated with computer system 102through manual or scheduled file system scans. Computer system 102 mayinclude internal and external hardware components, as depicted anddescribed in further detail with respect to FIG. 4.

Software assessment product 104 comprises schedule modifier 106, whichcan dynamically modify a schedule by which a file system scan willautomatically run. Schedule modifier 106 further comprises userinterface 107, computational subsystem 108 and schedule configuringsubsystem 109. By comparing results of a file system scan, e.g., a scanof computer system 102, with previous scans, schedule modifier 106 canalgorithmically determine a file system change value used to modify ascan schedule running on software assessment product 104, based on therate of file changes associated with computer system 102 that hasoccurred between scans. According to some embodiments of the presentinvention, computations used for the modification of a scan schedule caninvolve a plurality of preconfigured and/or dynamic variables, as willbe discussed in greater detail subsequently. It should also be notedthat according to some embodiments, schedule modifier 106 can be astand-alone program, downloadable onto computer system 102 and capableof communicating with software assessment product 104.

In various embodiments of the present invention, server computer 111 canbe a laptop computer, tablet computer, netbook computer, personalcomputer (PC), a desktop computer, a personal digital assistant (PDA), asmart phone, or any programmable electronic device capable ofcommunicating with computer systems 102 via network 110. In someembodiments, server computer 111 may be another computer system whichreceives the results of file system scans performed by softwareassessment product 104, running on computer system 102.

Network 110 can be, for example, a local area network (LAN), a wide areanetwork (WAN) such as the Internet, or a combination of the two, and caninclude wired, wireless, or fiber optic connections. In general, network110 can be any combination of connections and protocols that willsupport communications between computer system 102 and server computer111.

FIG. 2 is a flowchart 200 depicting operational steps of schedulemodifier 106 for dynamically modifying a file system scan schedule, inaccordance with an embodiment of the present invention. Schedulemodifier 106 receives, at step 202, the results of a first file systemscan of computer system 102, performed by software assessment product104. The results received may comprise, for example, the number of filesdetected by the first scan and the numbers of each type of filesignature detected. Schedule modifier 106 compares, at step 204, theresults received from the first scan with a previous scan, such as thelast scan run before the first scan, by accessing the previous scanresults through software assessment product 104. The comparison of scanresults can be used to determine information such as, but not limitedto, the change in the number of files detected between scans and thechange in the number of file signatures matched between scans, both ofwhich can be expressed as percentages.

Computational subsystem 108 computes, at step 206, a file system changevalue, based on a comparison of the results of a most recent scanagainst the results of a previous scan, e.g., the last scan run beforethe most recent scan. The frequency with which scheduled file systemscans will be performed by software assessment product 104 on computersystem 102 is modified, at step 208, by schedule configuring subsystem109, based on the computed file system change value.

It should be noted that according to some embodiments, schedule modifier106 can assign an initial predetermined file system consistency level tocomputer system 102, wherein a file system consistency level is a valueused by schedule configuring subsystem 109 to control the frequency ofscheduled file system scans performed by software assessment product104, based on preconfigured criteria. A file system consistency levelcan be, for example, a value on a scale from 0-100. A computed filesystem change value may therefore be applied to the file systemconsistency level of computer system 102 for modifying the frequency ofscheduled file system scans performed by software assessment product104.

It should further be noted that the computation of a file system changevalue and modification of the frequency of scheduled file system scanscan be dependent on a plurality of preconfigured or dynamically adjustedvariables, wherein the variables can be entered via user interface 107.Some examples of such variables can comprise, but are not limited to, amaximum allowed change value, a signatures factor, a change threshold, aminimum scan frequency and a maximum scan frequency.

A maximum allowed change value can be a value which limits how much afile system consistency level can change at once. A signatures factorcan be a multiplicative factor applied to a change in the number of filesignatures matched between scans. A change threshold can be a valuewhich to compare the result of a computation to for determining how afile system consistency level should be changed.

FIG. 3 is a flowchart 300 depicting operational steps of computationalprocesses performed by computational subsystem 108 for modifying a filesystem scan schedule, in accordance with one embodiment of the presentinvention. Based on received results of a most recent file system scanof computer system 102, computational subsystem 108 computes, at step302, the following sum:[% of file changes+(% change of file signatures matched*signaturefactor)]

Wherein “% of file changes” represents the percentage change in thenumber of files between file system scans and “% change of filesignatures matched” represents the percentage change of file signaturesmatched between file system scans. The sum computed at step 302 isapplied, as a percentage, to the preconfigured maximum allowed change atstep 304. For example, if the maximum allowed change is 10 and the sumis 60, embodiments will take 60% of 10 at step 304 for a result of 6.

The sum computed at step 302 is compared, at step 306, to thepreconfigured change threshold by computational subsystem 108. If therehas been a change in the number of file signatures matched (step 308,YES branch), the file system consistency level of computer system 102 isreduced at step 312 by the result of step 304, i.e., the result of step304 is a file system change value in this instance for changing the filesystem consistency level. In the case of the previous example, the fileconsistency level will be reduced by 6. Alternatively, if there is nochange in the number of file signatures matched (step 308, NO branch)but the sum is equal to or greater than the change threshold (step 310,YES branch), the file system consistency level will be reduced aspreviously described (step 312).

If there has been no change in the number of file signatures matched(step 308, NO branch) and the computed sum is less than the changethreshold (step 310, NO branch), the result of step 304 is subtractedfrom the maximum allowed change at step 314. In the case of the previousexample, wherein the result of step 304 is 6 and the maximum allowedchange is 10, computational subsystem 108 will accordingly compute[10-6] at step 314 for a result of 4. Computational subsystem 108increases the file system consistency level, at step 316, by the resultof step 314, e.g., 4, which is another example of a file system changevalue used to change the file system consistency level.

Based on the changes to the file system consistency level of computersystem 102 as a result of the computational processes depicted byflowchart 300, schedule configuring subsystem 109 can directly modifythe frequency of scheduled system scans performed by software assessmentproduct 104. As an illustrative example, assume that a minimum scanfrequency has been set to 1 week, a maximum scan frequency has been setto 25 weeks and computer system 102 has a file system consistency levelof 50 on a scale of 0-100, wherein a level of 0 corresponds to theminimum scan frequency and a level of 100 corresponds to the maximumscan frequency. According to this example, a file system consistencylevel of 50 approximately corresponds to a 12 week scan frequency, beingthat it is halfway between the minimum and maximum scan frequencies,which have a difference of 24 weeks. Schedule configuring subsystem 109will accordingly modify the frequency of scheduled file system scans tobe 12 weeks, based on the file system consistency level.

FIG. 4 depicts a block diagram 400 of components of computer system 102,in accordance with an illustrative embodiment of the present invention.It should be appreciated that FIG. 4 provides only an illustration ofone implementation and does not imply any limitations with regard to theenvironments in which different embodiments may be implemented. Manymodifications to the depicted environment may be made.

Computer system 102 includes communications fabric 402, which providescommunications between cache 416, memory 406, persistent storage 408,communications unit 410, and input/output (I/O) interface(s) 412.Communications fabric 402 can be implemented with any architecturedesigned for passing data and/or control information between processors(such as microprocessors, communications and network processors, etc.),system memory, peripheral devices, and any other hardware componentswithin a system. For example, communications fabric 402 can beimplemented with one or more buses or a crossbar switch.

Memory 406 and persistent storage 408 are computer readable storagemedia. In this embodiment, memory 406 includes random access memory(RAM). In general, memory 406 can include any suitable volatile ornon-volatile computer readable storage media. Cache 416 is a fast memorythat enhances the performance of computer processor(s) 404 by holdingrecently accessed data, and data near accessed data, from memory 406.

Software assessment product 104 and schedule modifier 106 can be storedin persistent storage 408 and in memory 406 for execution by one or moreof the respective computer processors 404 via cache 416. In anembodiment, persistent storage 408 includes a magnetic hard disk drive.Alternatively, or in addition to a magnetic hard disk drive, persistentstorage 408 can include a solid state hard drive, a semiconductorstorage device, read-only memory (ROM), erasable programmable read-onlymemory (EPROM), flash memory, or any other computer readable storagemedia that is capable of storing program instructions or digitalinformation.

The media used by persistent storage 408 can also be removable. Forexample, a removable hard drive can be used for persistent storage 408.Other examples include optical and magnetic disks, thumb drives, andsmart cards that are inserted into a drive for transfer onto anothercomputer readable storage medium that is also part of persistent storage408.

Communications unit 410, in these examples, provides for communicationswith other data processing systems or devices. In these examples,communications unit 410 includes one or more network interface cards.Communications unit 410 can provide communications through the use ofeither or both physical and wireless communications links. Softwareassessment product 104 and schedule modifier 106 can be downloaded topersistent storage 408 through communications unit 410.

I/O interface(s) 412 allows for input and output of data with otherdevices that can be connected to computer system 102. For example, I/Ointerface 412 can provide a connection to external devices 418 such as akeyboard, keypad, a touch screen, and/or some other suitable inputdevice. External devices 418 can also include portable computer readablestorage media such as, for example, thumb drives, portable optical ormagnetic disks, and memory cards. Software and data used to practiceembodiments of the present invention, e.g., Software assessment product104 and schedule modifier 106, can be stored on such portable computerreadable storage media and can be loaded onto persistent storage 408 viaI/O interface(s) 412. I/O interface(s) 412 also connect to a display420.

Display 420 provides a mechanism to display data to a user and can be,for example, a computer monitor.

The programs described herein are identified based upon the applicationfor which they are implemented in a specific embodiment of theinvention. However, it should be appreciated that any particular programnomenclature herein is used merely for convenience, and thus theinvention should not be limited to use solely in any specificapplication identified and/or implied by such nomenclature.

The present invention can be a system, a method, and/or a computerprogram product at any possible technical detail level of integration.The computer program product can include a computer readable storagemedium (or media) having computer readable program instructions thereonfor causing a processor to carry out aspects of the present invention.

The computer readable storage medium can be a tangible device that canretain and store instructions for use by an instruction executiondevice. The computer readable storage medium can be, for example, but isnot limited to, an electronic storage device, a magnetic storage device,an optical storage device, an electromagnetic storage device, asemiconductor storage device, or any suitable combination of theforegoing. A non-exhaustive list of more specific examples of thecomputer readable storage medium includes the following: a portablecomputer diskette, a hard disk, a random access memory (RAM), aread-only memory (ROM), an erasable programmable read-only memory (EPROMor Flash memory), a static random access memory (SRAM), a portablecompact disc read-only memory (CD-ROM), a digital versatile disk (DVD),a memory stick, a floppy disk, a mechanically encoded device such aspunch-cards or raised structures in a groove having instructionsrecorded thereon, and any suitable combination of the foregoing. Acomputer readable storage medium, as used herein, is not to be construedas being transitory signals per se, such as radio waves or other freelypropagating electromagnetic waves, electromagnetic waves propagatingthrough a waveguide or other transmission media (e.g., light pulsespassing through a fiber-optic cable), or electrical signals transmittedthrough a wire.

Computer readable program instructions described herein can bedownloaded to respective computing/processing devices from a computerreadable storage medium or to an external computer or external storagedevice via a network, for example, the Internet, a local area network, awide area network and/or a wireless network. The network can comprisecopper transmission cables, optical transmission fibers, wirelesstransmission, routers, firewalls, switches, gateway computers and/oredge servers. A network adapter card or network interface in eachcomputing/processing device receives computer readable programinstructions from the network and forwards the computer readable programinstructions for storage in a computer readable storage medium withinthe respective computing/processing device.

Computer readable program instructions for carrying out operations ofthe present invention can be assembler instructions,instruction-set-architecture (ISA) instructions, machine instructions,machine dependent instructions, microcode, firmware instructions,state-setting data, or either source code or object code written in anycombination of one or more programming languages, including an objectoriented programming language such as Smalltalk, C++ or the like, andconventional procedural programming languages, such as the “C”programming language or similar programming languages. The computerreadable program instructions can execute entirely on the user'scomputer, partly on the user's computer, as a stand-alone softwarepackage, partly on the user's computer and partly on a remote computeror entirely on the remote computer or server. In the latter scenario,the remote computer can be connected to the user's computer through anytype of network, including a local area network (LAN) or a wide areanetwork (WAN), or the connection may be made to an external computer(for example, through the Internet using an Internet Service Provider).In some embodiments, electronic circuitry including, for example,programmable logic circuitry, field-programmable gate arrays (FPGA), orprogrammable logic arrays (PLA) may execute the computer readableprogram instructions by utilizing state information of the computerreadable program instructions to personalize the electronic circuitry,in order to perform aspects of the present invention.

Aspects of the present invention are described herein with reference toflowchart illustrations and/or block diagrams of methods, apparatus(systems), and computer program products according to embodiments of theinvention. It will be understood that each block of the flowchartillustrations and/or block diagrams, and combinations of blocks in theflowchart illustrations and/or block diagrams, can be implemented bycomputer readable program instructions.

These computer readable program instructions can be provided to aprocessor of a general purpose computer, special purpose computer, orother programmable data processing apparatus to produce a machine, suchthat the instructions, which execute via the processor of the computeror other programmable data processing apparatus, create means forimplementing the functions/acts specified in the flowchart and/or blockdiagram block or blocks. These computer readable program instructionscan also be stored in a computer readable storage medium that can directa computer, a programmable data processing apparatus, and/or otherdevices to function in a particular manner, such that the computerreadable storage medium having instructions stored therein comprises anarticle of manufacture including instructions which implement aspects ofthe function/act specified in the flowchart and/or block diagram blockor blocks.

The computer readable program instructions can also be loaded onto acomputer, other programmable data processing apparatus, or other deviceto cause a series of operational steps to be performed on the computer,other programmable apparatus or other device to produce a computerimplemented process, such that the instructions which execute on thecomputer, other programmable apparatus, or other device implement thefunctions/acts specified in the flowchart and/or block diagram block orblocks.

The flowchart and block diagrams in the figures illustrate thearchitecture, functionality, and operation of possible implementationsof systems, methods, and computer program products according to variousembodiments of the present invention. In this regard, each block in theflowchart or block diagrams may represent a module, segment, or portionof instructions, which comprises one or more executable instructions forimplementing the specified logical function(s). In some alternativeimplementations, the functions noted in the block can occur out of theorder noted in the figures. For example, two blocks shown in successioncan, in fact, be executed substantially concurrently, or the blocks cansometimes be executed in the reverse order, depending upon thefunctionality involved. It will also be noted that each block of theblock diagrams and/or flowchart illustration, and combinations of blocksin the block diagrams and/or flowchart illustration, can be implementedby special purpose hardware-based systems that perform the specifiedfunctions or acts or carry out combinations of special purpose hardwareand computer instructions.

The descriptions of the various embodiments of the present inventionhave been presented for purposes of illustration, but are not intendedto be exhaustive or limited to the embodiments disclosed. Manymodifications and variations will be apparent to those of ordinary skillin the art without departing from the scope and spirit of the invention.The terminology used herein was chosen to best explain the principles ofthe embodiment, the practical application or technical improvement overtechnologies found in the marketplace, or to enable others of ordinaryskill in the art to understand the embodiments disclosed herein.

What is claimed is:
 1. A method for modifying a file system scanschedule, the method comprising: receiving first results of a first filesystem scan of one or more computer systems; comparing the first resultsto second results of a previous file system scan of the one or morecomputer systems; computing a file system change (FSC) value based onboth comparing the first results to the second results of the previousfile system scan and dynamically adjusted variables entered by a uservia a user interface based on the equation:FSC=% FC+(% SC*SF) where FSC=file system change value, % FC=thepercentage change in the number of files between file system scans, %SC=the percentage change of file signatures matched between file systemscans and SF=a predetermined signature factor; and modifying a frequencyof a file system scan schedule of scans performed by a softwareassessment product, based on the FSC.
 2. The method of claim 1, whereincomparing the first results to the second results comprises determininga change in a number of files detected between the first file systemscan and the previous file system scan and determining a change in anumber of file signatures matched between the first file system scan andthe previous file system scan.
 3. The method of claim 1, whereincomputing the file system change value is based on a plurality ofvariables comprising: a maximum allowed change value, a signaturesfactor, a change threshold, a minimum scan frequency and a maximum scanfrequency.
 4. The method of claim 1, wherein the one or more computersystems are assigned a file system consistency level, and wherein thefrequency is based on the file system consistency level.
 5. The methodof claim 4, wherein modifying the frequency comprises changing the filesystem consistency level using the file system change value.
 6. Themethod of claim 5, wherein computing the file system change valuecomprises computing a sum, based on comparing the first results to thesecond results, and taking the sum as a percentage of a maximum allowedchange value.
 7. The method of claim 6, wherein changing the file systemconsistency level is based on at least one of: comparing the sum to achange threshold and a determination of whether a change in a number offile signatures matched between the first file system scan and theprevious file system scan is detected.
 8. A computer program product formodifying a file system scan schedule, the computer program productcomprising: one or more computer readable storage media and programinstructions stored on the one or more computer readable storage media,the program instructions comprising: program instructions to receivefirst results of a first file system scan of one or more computersystems; program instructions to compare the first results to secondresults of a previous file system scan of the one or more computersystems; program instructions to compute a file system change (FSC)value based on both comparing the first results to the second results ofthe previous file system scan and dynamically adjusted variables enteredby a user via a user interface based on the equation:FSC=% FC+(% SC*SF) where FSC=file system change value, % FC=thepercentage change in the number of files between file system scans, %SC=the percentage change of file signatures matched between file systemscans and SF=a predetermined signature factor; and program instructionsto modify a frequency of a file system scan schedule of scans performedby a software assessment product, based on the FSC.
 9. The computerprogram product of claim 8, wherein the program instructions to comparethe first results to the second results comprise determining a change ina number of files detected between the first file system scan and theprevious file system scan and determining a change in a number of filesignatures matched between the first file system scan and the previousfile system scan.
 10. The computer program product of claim 8, whereinthe program instructions to compute the file system change value arebased on a plurality of variables comprising: a maximum allowed changevalue, a signatures factor, a change threshold, a minimum scan frequencyand a maximum scan frequency.
 11. The computer program product of claim8, wherein the one or more computer systems are assigned a file systemconsistency level, and wherein the frequency is based on the file systemconsistency level.
 12. The computer program product of claim 11, whereinthe program instructions to modify the frequency comprise changing thefile system consistency level using the file system change value. 13.The computer program product of claim 12, wherein the programinstructions to compute the file system change value comprise computinga sum, based on comparing the first results to the second results, andtaking the sum as a percentage of a maximum allowed change value. 14.The computer program product of claim 13, wherein changing the filesystem consistency level is based on at least one of: comparing the sumto a change threshold and a determination of whether a change in anumber of file signatures matched between the first file system scan andthe previous file system scan is detected.
 15. A computer system formodifying a file system scan schedule, the computer system comprising:one or more computer processors; one or more computer readable storagemedia; program instructions stored on the one or more computer readablestorage media for execution by at least one of the one or moreprocessors, the program instructions comprising: program instructions toreceive first results of a first file system scan of one or morecomputer systems; program instructions to compare the first results tosecond results of a previous file system scan of the one or morecomputer systems; program instructions to compute a file system change(FCS) value based on both comparing the first results to the secondresults of the previous file system scan and dynamically adjustedvariables entered by a user via a user interface based on the equation:FSC=% FC+(% SC*SF) where FSC=file system change value, % FC=thepercentage change in the number of files between file system scans, %SC=the percentage change of file signatures matched between file systemscans and SF=a predetermined signature factor; and program instructionsto modify a frequency of a file system scan schedule of scans performedby a software assessment product, based on the file FSC.
 16. Thecomputer system of claim 15, wherein the program instructions to comparethe first results to the second results comprise determining a change ina number of files detected between the first file system scan and theprevious file system scan and determining a change in a number of filesignatures matched between the first file system scan and the previousfile system scan.
 17. The computer system of claim 15, wherein the oneor more computer systems are assigned a file system consistency level,and wherein the frequency is based on the file system consistency level.18. The computer system of claim 17, wherein the program instructions tomodify the frequency comprise changing the file system consistency levelusing the file system change value.
 19. The computer system of claim 18,wherein the program instructions to compute the file system change valuecomprise computing a sum, based on comparing the first results to thesecond results, and taking the sum as a percentage of a maximum allowedchange value.
 20. The computer system of claim 19, wherein changing thefile system consistency level is based on at least one of: comparing thesum to a change threshold and a determination of whether a change in anumber of file signatures matched between the first file system scan andthe previous file system scan is detected.